| Author |
Thread Statistics | Show CCP posts - 14 post(s) |

Butter Dog
ISS Navy Task Force Interstellar Starbase Syndicate
|
Posted - 2006.08.29 21:54:00 -
[1]
Originally by: Malinaria More ships to come with kali heh ? YES but : - 4x Stealth bomber - 4x covert ops - 4x recon cruisers .... Woot ! 12 ships less, place for new ships i guess (memery shortage and stuff..
QFT... this is the first patch which has actually irritated me from a content perspective.
|

Butter Dog
ISS Navy Task Force Interstellar Starbase Syndicate
|
Posted - 2006.08.29 22:20:00 -
[2]
Edited by: Butter Dog on 29/08/2006 22:20:45
Originally by: Aelena Thraant Ok I tested the cloaking on the test server. The only thing that changed was now the covert ops decloaks on the covert ops ship. In otherwords.... if your close to locking the covert ops you will lock it but if your not then you won't...
Examples: (Using a Normal Lock time: 7 seconds)
A) Covert Ops decloaks Player starts Locking Covert Cloaks within a second or 2 = Target Lost B) Covert Ops decloaks Player starts Locking Covert Cloaks within 4 seconds of lock = Covert Cloaks Player shoots Covert decloaks
In other words... Cloaking ships are no longer a free pass thru gate camps if there is a fast locker... However if it's a slow locker... Well your safe unless you take a long time to cloak.
And what gate camp have you been to which doesnt have an interceptor present?
The Cov Ops thing is a f***ing joke. Never mind how its going to effect stealth bombers... they may as well be thrown in the bin.
|

Butter Dog
ISS Navy Task Force Interstellar Starbase Syndicate
|
Posted - 2006.08.30 00:06:00 -
[3]
Originally by: juduzz well just been on test server to test these "great" <-----a SUPER amount of saracsm here! and with an ares and no sensor boosting mods I could lock a buzzard AND scramble before he went to warp.
Yep eve is scrwed up now........
I've been trying to tell people this... 
|

Butter Dog
ISS Navy Task Force Interstellar Starbase Syndicate
|
Posted - 2006.08.30 01:30:00 -
[4]
Originally by: Turiya Flesharrower 1) Covert ops ships are supposed to be difficult to catch; by making them this vulnerable you are essentially retarding any chance of tactical fleet warfare. Covert ops scouts are heavily used as warp-ins and for checking ahead of moving fleets. No-one is going to fly a T2 ship that costs between 70 and 200 million ISK a pop if they know they'll die when they hit the first gate camp.
2) Server queues are probably the worst idea ever to come out of your development team since its conception. Do you have any idea how this is affecting 0.0 fleet movements? We've already encountered it ourselves and this was in a system with just 2 people in it; madness. You've coded a system for load balancing which directly contradicts the foundation of the queue system and your QA department then gave the green light for deployment onto both Tranquility and Serenity; fire them all now and hire people who can think more than 10 seconds ahead please.
3) I'll just say this; 5 BM limit on copying has got to be the laziest solution to this problem that could have been implemented. Ditto on the Cloaking issue; you've screwed over thousands of people in order to solve a problem which was experienced/caused by maybe hundreds at most and probably tens on average. There are plenty of alternate solutions with real promise just sitting here on your own forums. How about instead of implementing lazy quick-fixes you guys actually sit down and rewrite the system; you've had years to get this done and this is the best you can do?
Tell you what, I have a better idea than deploying out this 'patch' on Thursday; roll back the last one! Dragon brought nothing to the game that's actually of any use whatsoever and has actually made it a whole lot worse. I'd cheerfully lose a few days of skill training while you guys go through a full rollback or restore, the game was performing better beforehand anyway. Dragon is worthless.
Oh, and if Kali 1 is anything like this then I guarantee that you'll be flushing your reputation and subscriptions down the toilet on deployment day. And I know some smart-arse is going to give me the usual spiel about there being a separate content and programming team so I'll just say this; content has obviously out-run programming at this point. You're implementing new features too quickly and not spending enough time fixing existing problems; they just pile up and up and up. I'd be ecstatic if you guys just spent the next month or two on pure fixes (with proper QA) and put a total stop to Kali development until there's a stable foundation on which to base it.
Finally (phew) it was only recently that the dev team promised to actually improve communications with the community through the use of dev blogs and the forums. I now notice with chagrin that you've stopped completely, or rather, you're only communicating regarding issues that no-one gives a crap about at this point in time. I saw the queue system thread swell to 15+ pages in just a few days; no official response. Then someone posts a thread asking that the MOTD be changed; that got answered in about 15 minutes. How long could it possibly take for you guys to formulate a response to this situation and the community's concerns?
The best post in this thread, bar none.
|

Butter Dog
ISS Navy Task Force Interstellar Starbase Syndicate
|
Posted - 2006.08.30 15:12:00 -
[5]
Edited by: Butter Dog on 30/08/2006 15:12:03
Originally by: Arvo Henderson
Okay, they have quite a bit of CPU left after fitting the module to play with.
Er, try fitting a Cloak and Probe Launcher and see how much CPU you have left... oh, NONE.
In fact an Anathema with maxed out skills needs 2 Co-processor II fitted just to fit the 'essential' cov ops modules.
|

Butter Dog
ISS Navy Task Force Interstellar Starbase Syndicate
|
Posted - 2006.08.30 15:20:00 -
[6]
Originally by: Arvo Henderson
When you might die? When you turn up too close from the tacklers, or a insta-lock sniping BS (which is fantasy - Booster Stacking nerf). But again, you can stab your ship. Yes, you won't have much CPU to fit fancy weapons, fit ECM stuff instead. You can try to dampen/jam the snipers/tacklers - you'll lock the sniper BS much faster than him can.
You don't have the first clue what you are talking about, and clearly have no experience actually fitting and using Covert Ops ships.
You CANNOT fit stabs on covert ops ships without offlining either the cloak or probe launcher. FACT.
As someone demonstrated on the test server, an Ares with no sensor booster and a 20km scram under the current patch conditions, can LOCK and SCRAM a covert ops before it even enters warp. They are not the most agile of ships.
This means, dictor bubbles aside, that a single ceptor on a gate with one 20km scram = CERTAIN DEATH for covert ops.
|

Butter Dog
ISS Navy Task Force Interstellar Starbase Syndicate
|
Posted - 2006.08.30 15:22:00 -
[7]
Originally by: Arvo Henderson
Fit the Probe launcher if you want. But it doesn't need to be online unless you're going to use it, or you will be using it while trying to break through a camp?. Get to a safespot, offline the cloak and online the probe launcher.
What and then sit there unable to warp to your results while you wait for you cap to get up to 95%? Get real.
|

Butter Dog
ISS Navy Task Force Interstellar Starbase Syndicate
|
Posted - 2006.08.30 15:31:00 -
[8]
Originally by: Arvo Henderson
How much cap does eat a probe launcher? Not much. How fast is the cap recharge rate in a Helios with capacitor skills maxed (or at level 4)? Fast. How long take your probes to yield any result? Longer than your cap recharges to 100%.
Do you need to have the scan probe launcher online for the probes to work (once launched, ofc)? I haven't ever tried to do that It wasn't necessary 
What are you talking about? Are you even playing the same game as me?
To online an offline module requires 95% cap, and uses most of that to online the module. However, to online the probe launcher you would have to offline the cloak if you had no CPU II's fitted.
Obviously you can't warp to a target uncloaked, so you would have to wait for your cap to regen to 95% before onlining the cloak again. This is frankly ridiculous.
Give it up, because you lost the argument the moment Tux said things WERE being returned to the pre-Dragon stage.
|
| |
|